NOTE: AppleScript 1.1 or later is HIGHLY recommended!
Previous versions of Folder Watcher would not always execute AppleScripts properly for one reason or another. I'm not completely convinced it was 100% Folder Watcher's fault but this fix should make things work "as advertised" in most (if not all) cases.
When told to execute an AppleScript, Folder Watcher used to look for "Compiled Script" documents. It would then open these documents, load their contents, and attempt to execute them. They would sometimes work the first time but not subsequent times. This bug was very strange and not 100% reproducible.
Version 2.0.3 of Folder Watcher addresses this problem. Folder Watcher no longer looks for compiled script documents ending in ".scr", it now looks for AppleScripts saved as Applications (via the Apple Script Editor) with the suffix ".app" and will launch any it finds.
So, if you have a folder named "My Folder" and an application (or alias to an application) in the Folder Watcher Aliases folder called "My Folder.app", it will be launched when the folder changes. Read the Folder Watcher documentation for complete instructions on how this works. The only differences are:
• Folder Watcher now LAUNCHES APPLICATIONS as opposed to EXECUTING SCRIPT DOCUMENTS.
• Folder Watcher now looks for files ending in ".app" as opposed to ".scr"
To convert your existing AppleScripts, simply open the documents in the Script Editor, select Save As... and choose to save them as an Application. That's it!
If you get -39 errors when a folder changes, it means your ".app" file is not an application. And yes, your application can be anything you want, not just an AppleScript application. Heck, you can launch Microsoft Word if you want.
Please report successes and failures to me...see the documentation for my email address. Thanks!
